Skip to content

build(deps): bump @stellar/stellar-sdk from 15.1.0 to 16.0.1#779

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/stellar/stellar-sdk-16.0.1
Open

build(deps): bump @stellar/stellar-sdk from 15.1.0 to 16.0.1#779
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/stellar/stellar-sdk-16.0.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 22, 2026

Copy link
Copy Markdown
Contributor

Bumps @stellar/stellar-sdk from 15.1.0 to 16.0.1.

Release notes

Sourced from @​stellar/stellar-sdk's releases.

v16.0.1

v16.0.1

Fixed

  • Fixed the ESM library build so the inlined @stellar/js-xdr source resolves correctly under Yarn PnP (and Node's native ESM resolver). Because the build preserves modules, Rollup emits js-xdr's source into a nested package scope, but js-xdr does not declare type: "module", so Node and Yarn PnP parsed those preserved files as CommonJS and failed to resolve them. Rollup now marks the emitted js-xdr package as type: "module" so its source is parsed as ESM #1484.

Full Changelog: stellar/js-stellar-sdk@v16.0.0...v16.0.1

v16.0.0

v16.0.0

Migration guide

There are a few major updates in this release:

  • JS Stellar Base (@stellar/stellar-base) was rewritten in TypeScript, which provides proper type definitions and fixes inconsistencies caused by manual type declarations. (#1399)
  • JS Stellar Base is now merged into the JS Stellar SDK. Everything lives in one place now. (#1399)
  • The JS SDK now has better tree-shaking, which should result in a lighter bundle size. (#1397)
  • Protocol 27 support: the XDR was regenerated for CAP-71, and the Soroban authorization helpers can build and sign the new address-bound (SOROBAN_CREDENTIALS_ADDRESS_V2) and delegated (SOROBAN_CREDENTIALS_ADDRESS_WITH_DELEGATES) credential types. The legacy SOROBAN_CREDENTIALS_ADDRESS (V1) credential remains the default; ADDRESS_V2 is opt-in (see below), as it is only valid on networks that have activated CAP-71. (#1429, #1450)

1. Breaking Changes

These break code, builds, or installs until you change something.

Install & runtime

  • Drop @stellar/stellar-base from your dependencies if you were importing it manually. It is now bundled into @stellar/stellar-sdk. Remove the package and switch all imports from @stellar/stellar-base to @stellar/stellar-sdk. (#1399)
  • Upgrade to Node 22 or later. engines.node is now >=22.0.0; CI tests against [22, 24]. (#1408)

... (truncated)

Changelog

Sourced from @​stellar/stellar-sdk's changelog.

v16.0.1

Fixed

  • Fixed the ESM library build so the inlined @stellar/js-xdr source resolves correctly under Yarn PnP (and Node's native ESM resolver). Because the build preserves modules, Rollup emits js-xdr's source into a nested package scope, but js-xdr does not declare type: "module", so Node and Yarn PnP parsed those preserved files as CommonJS and failed to resolve them. Rollup now marks the emitted js-xdr package as type: "module" so its source is parsed as ESM #1484.

v16.0.0

There are a few major updates in this release:

  • JS Stellar Base (@stellar/stellar-base) was rewritten in TypeScript, which provides proper type definitions and fixes inconsistencies caused by manual type declarations. (#1399)
  • JS Stellar Base is now merged into the JS Stellar SDK. Everything lives in one place now. (#1399)
  • The JS SDK now has better tree-shaking, which should result in a lighter bundle size. (#1397)
  • Protocol 27 support: the XDR was regenerated for CAP-71, and the Soroban authorization helpers can build and sign the new address-bound (SOROBAN_CREDENTIALS_ADDRESS_V2) and delegated (SOROBAN_CREDENTIALS_ADDRESS_WITH_DELEGATES) credential types. The legacy SOROBAN_CREDENTIALS_ADDRESS (V1) credential remains the default; ADDRESS_V2 is opt-in (see below), as it is only valid on networks that have activated CAP-71. (#1429, #1450)

1. Breaking Changes

These break code, builds, or installs until you change something.

Install & runtime

  • Drop @stellar/stellar-base from your dependencies if you were importing it manually. It is now bundled into @stellar/stellar-sdk. Remove the package and switch all imports from @stellar/stellar-base to @stellar/stellar-sdk. (#1399)
  • Upgrade to Node 22 or later. engines.node is now >=22.0.0; CI tests against [22, 24]. (#1408)
  • Stop using the default import. import StellarBase from '@stellar/stellar-sdk' no longer works. Use import * as StellarBase or named imports. (#1396)
  • Adjust deep lib/ imports. Library output paths moved:
    • ESM at lib/esm/,
    • CJS at lib/cjs/,
    • axios variants at lib/axios/esm/ and lib/axios/cjs/,

... (truncated)

Commits
Install script changes

This version modifies prepare script that runs during installation. Review the package contents before updating.


@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jun 22, 2026
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/stellar/stellar-sdk-16.0.1 branch from 8db70b4 to 1089a34 Compare June 29, 2026 13:24
Bumps [@stellar/stellar-sdk](https://github.com/stellar/js-stellar-sdk) from 15.1.0 to 16.0.1.
- [Release notes](https://github.com/stellar/js-stellar-sdk/releases)
- [Changelog](https://github.com/stellar/js-stellar-sdk/blob/master/CHANGELOG.md)
- [Commits](stellar/js-stellar-sdk@v15.1.0...v16.0.1)

---
updated-dependencies:
- dependency-name: "@stellar/stellar-sdk"
  dependency-version: 16.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/stellar/stellar-sdk-16.0.1 branch from 1089a34 to 2b436f3 Compare June 29, 2026 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants